System and method for retrieval and analysis of operational data from customer, cloud-hosted virtual resources

ABSTRACT

A system for protecting public cloud-hosted virtual resources features cloud visibility logic. According to one embodiment, the cloud visibility logic includes credential evaluation logic, data collection logic, correlation logic and reporting logic. The credential evaluation logic is configured to gain authorized access to a cloud account within a first public cloud network. The data collection logic is configured to retrieve account data from the cloud account, while the correlation logic is configured to conduct analytics on the account data to determine whether the cloud account is subject to a cybersecurity threat or misconfiguration. The reporting logic is configured to generate an alert when the cloud account is determined by the correlation logic to be subject to the cybersecurity threat or misconfiguration.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is based upon and claims the benefit of priority from U.S. Provisional Patent Application No. 62/824,300 filed Mar. 26, 2019, the entire contents of which are incorporated herein by reference.

FIELD

Embodiments of the disclosure relate to the field of network services. More specifically, one embodiment of the disclosure relates to a system configured to protect cloud-hosted resources.

GENERAL BACKGROUND

In the past, businesses have relied on application software installed on one or more electronic device residing in close proximity to its user (hereinafter, “on-premises electronic devices”). Each on-premises electronic device may constitute a type of computer such as a personal computer, a locally maintained mainframe, or a local server for example. Recently, however, more businesses and individuals have begun to rely on public cloud networks for their data computing and storage needs.

In general, a “public cloud network” is a collection of data centers, where each data center includes numerous servers and is hosted by a service provider. The data centers offer resources, such as virtual compute engines (e.g., virtual machines), application instances, and virtual data stores for example, which are available to the general public over the Internet. These resources may be free to the public or may be offered on a pay-per-usage basis. For instance, payments for data processing resources may be based on hourly compute time while payments for data storage resources may be based on the amount of storage being used (e.g., per megabyte, per gigabyte, etc.).

As a result, for a public cloud deployment, individuals are able to remotely access and utilize numerous services offered by a plurality of resources, including virtual compute engines that execute different types of applications and virtual persistent data storage. Examples of current public cloud networks may include, but are not limited or restricted to Amazon Web Services®, Microsoft Azure®, Google Cloud®, or the like (collectively referred to as the “cloud”).

This growing migration to the cloud is due, in large part, to a number of advantages offered by the cloud. For instance, the cloud is a fully virtualized environment with a multi-tenant architecture that enables tenants (i.e., “customers”) to establish different cloud accounts but share computing and storage resources. Data within each customer's cloud account, however, remains isolated from other customers. Hence, cloud-based services are ideal for businesses with growing or fluctuating resource demands, as the cloud capacity for virtual resources (e.g., compute power, data storage, etc.) is scalable and the usage-based cost structure does not require an entity to invest a large amount of capital in requisite hardware and/or software.

Additionally, unlike on-premises deployments, software updates and modifications for a customer are routinely handled by the cloud service provider without customer involvement. As a result, customers may realize labor and cost savings on network support expenditures. However, the lack of customer involvement in evaluating software updates and modifications to the virtual resources (e.g., application instances, virtual stored data, virtual compute engines, etc.) may pose significant risks, such as an increased risk of the customer's cloud account becoming compromised and/or an increased risk of cloud account setting misconfigurations caused by accident due to the increased complexity of public cloud networks or caused by unexpected setting changes.

Stated differently, given the rapid migration to public cloud networks, which are accessible by multiple users, there is now a growing tendency of cloud accounts (user accounts within the public cloud network) being subjected to attack and compromise. One type of attack is referred to as a “cyberattack,” which constitutes a threat to the security and/or intended operability of a virtual resources offered as part of the cloud-host resources. The cyberattack may involve infiltration of content into data storage resources (e.g., a cloud storage service such as Amazon® S3), where the content may include one or more executables (e.g., scripts, one or more commands, programs, etc.) or one or more non-executables (e.g., modification of metrics or settings within stored files, etc.), each being designed to perpetrate unwanted, malicious or criminal activity. In addition to or in lieu of a cyberattack, cloud-hosted resources may experience certain operational issues that may occur through intentional or unintentional account misconfiguration, which may be caused by the user or the cloud service provider (e.g., abnormal configuration settings, unexpected transmission format setting changes such as disabling or enabling encryption, etc.).

Currently, there are no trusted third party schemes available for customers to effectively and easily analysis cloud accounts in efforts to detect whether cloud-hosted resources have been compromised or misconfigured accidentally or intentionally.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

FIG. 1 is a block diagram of an exemplary embodiment a plurality of public cloud networks deploying cloud resource monitoring systems each configured to access specific customer cloud accounts, analyze information within these cloud accounts, aggregate information between cloud accounts in different public cloud networks, and report the analytic results therefrom.

FIG. 2 is an exemplary embodiment of virtual resources within the first public cloud network of FIG. 1 including the cloud resource monitoring system including cloud visibility logic interacting with virtual resources within a cloud account.

FIG. 3 is an exemplary embodiment of a user interface portal (Web UI) that is generated during customer registration to provide access permissions of account resources to the cloud visibility logic.

FIG. 4A is an exemplary embodiment of virtual resources within the first public cloud network of FIG. 1 including the cloud visibility logic being part of the cloud resource monitoring system installed within a customer's cloud account.

FIG. 4B is an exemplary embodiment of cloud visibility logic of FIG. 4A along with its operability with virtual resources within the cloud account.

FIG. 5A is an exemplary embodiment of a dashboard generated by the cloud visibility logic to provide collected diagnostic data to a customer administrator relying on cloud account management services.

FIG. 5B is an exemplary embodiment of a first navigational tool that is accessible through the dashboard of FIG. 5A and controlled by the cloud visibility logic to generate a display of the inventory of virtual resources utilized by the customer's cloud account.

FIG. 5C is an exemplary embodiment of a second navigational tool that is accessible through the dashboard of FIG. 5A and controlled by the cloud visibility logic to generate a display of the resource infrastructure for the customer's cloud account.

FIG. 5D is an exemplary embodiment of a third navigational tool that is accessible through the dashboard of FIG. 5A and generated by the cloud visibility logic to provide a listing of malicious or compromising events conducted by virtual resources within the customer's cloud account.

FIG. 6 is an exemplary embodiment of resources associated with the first public cloud network of FIG. 1 including the cloud visibility logic installed within an on-premises electronic device that is configured to access and retrieve specific customer account information for analysis within the on-premises electronic device.

FIG. 7 is an exemplary embodiment of resources associated with the first public cloud network of FIG. 1 illustrating operations conducted by a hybrid cloud management system including cloud visibility data collection logic maintained at the public cloud network and cloud visibility analytic logic maintained at an on-premises electronic device.

FIG. 8 is an exemplary flowchart of the operations conducted by the cloud resource monitoring system.

DETAILED DESCRIPTION

Embodiments of the present disclosure generally relate to a cloud resource monitoring system that is configured to protect customer cloud-hosted resources within a public cloud network. Herein, cloud visibility logic, operating as part of the cloud resource monitoring system, may be configured to gain access to, ingest, and perform analytics on data from cloud-hosted resources specific to one or more cloud accounts for targeted customer(s). This “account data” may include operational log data or other types of meta-information. The analytics are conducted in order to identify whether a cloud account has been potentially compromised (e.g., potential cybersecurity threat) as well as any cloud account misconfigurations, whether intentional or unintentional. As a result, administrators and analysts may access a single location (e.g., display generated by the cloud resource monitoring system, and in particular, the cloud visibility logic) to review the security status of all cloud services provided within the cloud accounts.

Herein, the operational log data may include information that pertains to an event performed by a customer's cloud-hosted virtual resources. The “event” may correspond to an operation or a collection of operations conducted by one or more virtual resources of a (customer) cloud account, where the operation(s) cause a change of state in the cloud account's infrastructure. As an illustrative example, an event may include an Application Programming Interface (API) call that is intended to create, modify, or read data, where information associated with the API call is recorded and stored within an entry of an API log stored within the cloud account. The information within entries of the API log constitutes one type of operational log data. As another illustrative example, an event may include an operation performed by a virtual compute engine, where information associated with that operation (e.g., identifier of virtual compute engine, processing time, type of operation performed, results of the operation, etc.) is recorded and stored in one or more entries within another operational (compute) log. This information constitutes another type of operational log data.

Besides operational log data, the account data collected from the cloud account may include flow data. The flow data may include meta-information associated with the interconnectivity between virtual resources or other types of meta-information such as information directed to the software infrastructure of the cloud account.

During or after analytics are conducted on the account data, the cloud visibility logic may be further configured to provide a visualization of the infrastructure of the cloud account, which may allow an administrator to identify changes to the cloud-hosted resources by visual inspection of the cloud account infrastructure. These changes may indicate that one or more virtual resources associated with the cloud account under analysis has been compromised or misconfigured. In some embodiments, the visualization may be based on a comparison of different snapshots of cloud-hosted resources securely maintained within a data store within the cloud account. The similarities and/or differences may be used to identify certain types of events (e.g., resource changes, configuration changes, etc.) and provide a timeline as to the occurrence of these changes.

As a result, upon detecting that a virtual resource has been compromised or misconfigured, the cloud resource monitoring system allows for a retrospective review of that virtual resource. In particular, as the operational log data may be maintained for a prolonged duration (e.g., one year) within cloud or local (e.g., on-premises) storage, administrators may be able to gather historical operational data associated with compromised or misconfigured cloud-based virtual resource (e.g., Critical configuration/policy changes and user identification associated with the changes, time the compromise or misconfiguration occurred, responsible party, compliance violations, administrator at time of the compromise/misconfiguration, alerts generated, any remediation attempts as well as the time and successfulness of the remediation, etc.).

Based on the results of the analytics, the cloud visibility logic may control the reporting of the analytic results, which may include one or more dashboards that provide an administrator (e.g., person responsible for managing the customer cloud-hosted resources or the public cloud network itself) access to alerts. Additionally, for compliance with certain cloud policies, upon detection of a potential cybersecurity threat and/or misconfiguration, the cloud visibility logic may initiate actions to remediate the detected cybersecurity threat and/or misconfiguration through blocking, resetting of configuration settings, or the like.

As a collective summary, the cloud resource monitoring system is responsible for monitoring and protecting the customer cloud account(s) against attack and/or misconfiguration. As described herein, the cloud resource monitoring system may be provided as (i) logic (e.g., a piece of software such as an instance) deployed within a protected customer cloud account (FIGS. 5A-5B) or logic maintained within virtual resources separate from the customer cloud account (e.g., virtual resources within the public cloud network that are maintained by the network provider or a third party (FIG. 2)). As another alternative embodiment, in lieu of deployment within the public cloud network, the cloud resource monitoring system may be implemented within an on-premises electronic device. For this embodiment, the cloud resource monitoring system may be configured to establish communications with one or more public cloud networks to access customer cloud account(s), and then, collect data (e.g., operational log data) from the customer cloud account(s) for storage within one or more data stores maintained within the on-premises electronic device or another electronic device. As yet another embodiment, a hybrid deployment may be utilized in which data collection logic of the cloud visibility logic is maintained at the public cloud network while data analytics logic of the cloud visibility logic is maintained at the on-premises electronic device.

In monitoring and protecting customer cloud account(s), the cloud resource monitoring system, in particular its cloud visibility logic, may be configured to (i) gain authorized access to a particular customer's cloud account; (ii) collect data (e.g., meta-information including operational log data) from virtual data stores pertaining to the accessed cloud account; (iii) generate a display that visualizes the infrastructure of the accessed cloud account with display elements corresponding to virtual resources within the accessed cloud account that, upon selection, may provide greater granularity as to the properties and operations associated with these virtual resources; (iv) perform analytics of the collected data to determine a presence of any cybersecurity threats or account misconfigurations; and/or (v) perform activities to alert one or more administrators of the analytic results and/or to conduct any remediation, if desired. Additionally, the cloud resource monitoring system may be configured to aggregate its analytic results with results from multiple (two or more) cloud accounts to generate a single display (dashboard) to visually depict the presence of any potential cybersecurity threats or misconfigurations for cloud accounts from multiple different public cloud networks. Additionally, or in the alternative, the cloud resource monitoring system may be configured to retrieve and aggregate data (e.g., operational log data) received from cloud accounts residing in different public cloud networks, perform analytics on the aggregated data, and generate a display (dashboard) to visually depict the presence of any potential cybersecurity threats or misconfigurations for any of these cloud accounts.

According to one embodiment of the disclosure, the cloud resource monitoring system may be configured to obtain authorized access to a particular customer's cloud account in a public cloud network using any of a number of authentication schemes. For example, one authentication scheme may feature a web user interface (UI) portal that is made available after selection by a customer of the cloud resource monitoring system offered by a public cloud network provider or a third party.

More specifically, the web UI portal or command line interface (CLI) is provided to receive credentials from the customer in order to get access token. The credentials are made available to the cloud visibility logic, which may be configured to communicate the customer credentials to access control logic for the public cloud network. Upon successful customer authentication, access token is returned to the cloud visibility logic. The access token enable the cloud visibility logic to commence a communication (monitoring) session to gain authorized access to content within the customer's cloud account(s). The access token may identify specific virtual resources to which the cloud visibility logic is provided access or may provide account-wide access to data therein. Alternatively, a Security Token Service (STS) may be deployed within the public cloud network to generate access token through a web service that generates, upon request, temporary, limited-privilege credentials (access tokens) for use by the cloud visibility logic managed by authenticated users (e.g. Amazon Web Service “AWS” Identity and Access Management “IAM” users) or other authorized users.

Once granted authorization, according to one embodiment of the disclosure, the cloud visibility logic may collect data (e.g., operational log data acquired and/or generated during the processing of software components by virtual compute engines allocated to the customer's cloud account) stored within one or more virtual data stores allocated to that cloud account. Alternatively, according to another embodiment of the disclosure, the cloud visibility logic may acquire the above-described collected data from the customer's cloud account, but the collected data may be stored within one or more virtual data stores assigned to a different cloud account.

As described above, the cloud visibility logic may perform analytics on the collected data to detect a cybersecurity threat and/or cloud account misconfiguration. According to one embodiment of the disclosure, the analytics may involve one or more analyses of the collected data (e.g., operational log data, etc.), which are conducted in accordance with a plurality of rules that are chosen to identify an occurrence of one or more unexpected, abnormal or inconsistent events. The analyses may involve a matching of events associated with the collected data with patterns of known suspicious events such as patterns of known malicious events or patterns of events (e.g., activities) previously used by hackers to misconfigure and compromise a cloud account or services within the cloud account (hereinafter “compromising events), which may involve an initial temporal analysis being conducted to place these suspicious events in some sort of chronological order based on time of occurrence. Additionally, or in the alternative, the analyses may involve a comparison of the current snapshot of the state of the cloud account against the prior snapshots. Thereafter, an analysis is conducted on the differences between these snapshots to determine changes in the cloud account. For both of these analyses, the cloud visibility logic operates to determine potential issues, such as cybersecurity threats or misconfigurations, both intentional misconfigurations as part of a cybersecurity attack or accidental misconfigurations, that may be causing the virtual resources for an account to operate incorrectly, inconsistently, or in a less than optimal manner.

Besides detecting potential issues as described above, the cloud visibility logic is configured to analyze the collected data retrieved from operational logs by at least determining characteristics shared by different operational log data (e.g., common sources, activity or activities that caused generation of the operational logic data, etc.). The collected data is further analyzed to learn relationships amongst the operational log data, which may generate additional meta-information for use in the analytics of the collected operational log data. This additional meta-information may be aggregated and correlated with known patterns of malicious activity or compromising activity via configuration changes (e.g., settings, permissions, etc.) to further assist in determining a cybersecurity threat or account misconfiguration.

Determination of a cybersecurity threat or account misconfiguration may be further established by the cloud visibility logic correlating the collected data associated with the one or more cloud accounts with heuristic information such as cybersecurity threat information from other systems or third-party systems (e.g., machine generated intelligence, post-intrusion intelligence, pre-attack intelligence, etc.). Other examples of heuristic information may include, but is not limited or restricted to expected account configuration setting and/or configuration setting misconfigurations that have been determined to be more susceptible to cybersecurity attack or adversely affect operability of certain virtual resources.

The collective analytics on the heuristic information and the collected data, as described above, may generate a score that denotes a presence of a cybersecurity threat or an account misconfiguration. In some embodiments, known cybersecurity threats may be mitigated through a prescribed mitigation scheme.

If cybersecurity threat or account misconfiguration is detected, an alert may be generated and issued to one or more administrators. If a prescribed mitigation scheme exists to remediate a detected cybersecurity threat or account misconfiguration, the cloud management system may generate an alert for an administrator and provide the prescribed mitigation scheme, which may be triggered automatically or may be controlled by an administrator (e.g., selecting a radio button or link to provide further information of the threat/misconfiguration and potential mitigation processes available). The alerts and/or prescribed mitigation scheme may be configured in accordance with a set of regulatory compliance rules associated with, for example, regulatory compliance (e.g., Health Insurance Portability and Accountability Act (HIPAA), Payment Card Industry Data Security Standard (PCI DSS), etc.).

I. Terminology

In the following description, certain terminology is used to describe aspects of the invention. In certain situations, the terms “logic” and “engine” are representative of hardware, firmware, and/or software that is configured to perform one or more functions. As hardware, the logic (or engine) may include circuitry having data processing and/or storage functionality. Examples of such circuitry may include, but are not limited or restricted to a processor, a programmable gate array, a microcontroller, an application specific integrated circuit, wireless receiver, transmitter and/or transceiver circuitry, semiconductor memory, or combinatorial logic.

Alternatively, or in combination with the hardware circuitry described above, the logic (or engine) may be software in the form of one or more software modules. The software modules may include an executable application, a daemon application, an application programming interface (API), a subroutine, a function, a procedure, an applet, a servlet, a routine, source code, a shared library/dynamic load library, or even one or more instructions. The software module(s) may be stored in any type of a suitable non-transitory storage medium, or transitory storage medium (e.g., electrical, optical, acoustical or other form of propagated signals such as carrier waves, infrared signals, or digital signals). Examples of non-transitory storage medium may include, but are not limited or restricted to a programmable circuit; a semiconductor memory; non-persistent storage such as volatile memory (e.g., any type of random access memory “RAM”); persistent storage such as non-volatile memory (e.g., read-only memory “ROM”, power-backed RAM, flash memory, phase-change memory, etc.), a solid-state drive, hard disk drive, an optical disc drive, or a portable memory device. As firmware, the logic (or engine) may be stored in persistent storage.

The term “electronic device” should be generally construed as electronics with data processing capability and/or a capability of connecting to any type of network, such as a public cloud network (e.g., Amazon Web Service (AWS®), Microsoft Azure®, Google Cloud®, etc.), a private cloud network, or any other network type. Examples of an electronic device may include, but are not limited or restricted to, the following: a server, a mainframe, a firewall, a router or other intermediary communication device, or an endpoint device (e.g., a laptop, a smartphone, a tablet, a desktop computer, a netbook, gaming console, etc.).

The term “meta-information” generally refers to a collection of information that is descriptive of characteristics of a certain portion of information to which the meta-information pertains. For example, the meta-information may identify the portion of information for purposes of discovery and/or identification. As another example, the meta-information may identify structural or administrative characteristics for the portion of information such as (1) data type, (2) version, (3) relationships to other information, (4) access history or controls (e.g., permissions, access content directed to user/time/source, etc.), (5) creation or modification history (e.g., when portion of information created or modified, when/what processes created from the information, etc.), or the like.

The term “message” generally refers to signaling (wired or wireless) as either information placed in a prescribed format and transmitted in accordance with a suitable delivery protocol or information made accessible through a logical data structure such as an API. Examples of the delivery protocol include, but are not limited or restricted to HTTP (Hypertext Transfer Protocol); HTTPS (HTTP Secure); Simple Mail Transfer Protocol (SMTP); File Transfer Protocol (FTP); iMES SAGE; Instant Message Access Protocol (IMAP); or the like. Hence, each message may be in the form of one or more packets, frames, or any other series of bits having the prescribed, structured format.

The term “computerized” generally represents that any corresponding operations are conducted by hardware in combination with software and/or firmware.

As described herein, a cloud management system may be deployed as a “cloud-based hosted service,” a “hosted service,” or a combination thereof, any of which operates to protect customer cloud-hosted resources maintained within a public cloud network. A cloud-based hosted service may be configured to operate as a multi-tenant service; namely a service made available to tenants (also referred to as “customers”) on demand via a public network (e.g., Internet). The multi-tenant service may feature virtual resources, such as virtual compute engines and/or virtual data stores for example, which are partitioned for use among the customers in accessing and/or analyzing data maintained within that customer's specific cloud account. The partitioning protect the security and privacy of the customer data. A “hosted service” may be configured as a single-tenant service provided by a customer's own on-premises server(s) to access and collect meta-information from that customer's cloud accounts(s). Examples of a hosted service may include, but is not limited or restricted to a Microsoft® Exchange® server, a file repository, or the like.

In certain instances, the terms “compare,” comparing,” “comparison,” or other tenses thereof generally mean determining if a match (e.g., identical or a prescribed level of correlation) is achieved between meta-information associated with two items under analysis.

The term “transmission medium” generally refers to a physical or logical communication link (or path) between two or more network devices. For instance, as a physical communication path, wired and/or wireless interconnects in the form of electrical wiring, optical fiber, cable, bus trace, or a wireless channel using infrared, radio frequency (RF), may be used.

Finally, the terms “or” and “and/or” as used herein are to be interpreted as inclusive or meaning any one or any combination. As an example, “A, B or C” or “A, B and/or C” mean “any of the following: A; B; C; A and B; A and C; B and C; A, B and C.” An exception to this definition will occur only when a combination of elements, functions, steps or acts are in some way inherently mutually exclusive.

As this invention is susceptible to embodiments of many different forms, it is intended that the present disclosure is to be considered as an example of the principles of the invention and not intended to limit the invention to the specific embodiments shown and described.

II. Cloud Management System Deployments

Referring to FIG. 1, a block diagram of an exemplary embodiment of a cloud resource monitoring system 100 operating in cooperation with one or more public cloud networks 110 ₁-110 _(N) (N≥1) to access and analyze content within specific user accounts deployed in the public cloud network(s) is shown. Each of the public cloud networks 110 ₁-110 _(N) (e.g., Microsoft Azure®, or Amazon Web Services®, or Google Cloud®, etc.) is a fully virtualized, multi-tenant service made available through one or more data centers 120. As shown, with respect to a first public cloud network 110 ₁ for example, the data center(s) 120 may include a plurality of servers 125 maintained by a provider of the first public cloud network 110 ₁. The servers 125 include logic, operating as virtual resources, which are offered by the first public cloud network 110 ₁ and made available to the general public over the Internet.

Herein, the operations of the cloud resource monitoring system 100 (deployed within the first public cloud network 110 ₁) are directed to gaining authorized access to information within a cloud account 130 associated with a specific tenant (hereinafter referred to as a “customer”), where the accessing entity is different than the customer. The cloud account 130 corresponds to a collection of virtual resources allocated to the customer, where the cloud account 130 is hosted at a public cloud network (e.g., the first public cloud network 110 ₁).

It is contemplated that multiple (two or more) cloud accounts 130 and 132 for a particular customer may be hosted at different public cloud networks (e.g., the first public cloud network 110 ₁ and N^(th) public cloud network 110 _(N)). For this deployment, the cloud resource monitoring system 100 is configured to monitor/protect customer cloud-hosted resources of and operate within the first public cloud network 110 ₁ while another cloud resource monitoring system 102 may be configured to monitor/protect customer cloud-hosted resources of and operate within the N^(th) public cloud network 110 _(N). For simplicity, the cloud resource monitoring management services described herein will focus on the operability of the cloud resource monitoring system 100 installed within the first public cloud network 110 ₁.

After gaining access to the customer's cloud account 130, the cloud resource monitoring system 100 may be configured to collect account data 140 (referred to as “collected data 140”) from the accessed cloud account 130 (e.g., operational log data, meta-information directed to virtual resources being utilized within the cloud account 130 such as virtual compute engines or virtual data stores, etc.). According to one embodiment of the disclosure, a portion of the collected data 140 may be used in the generation of a display 150, which visualizes the infrastructure of the accessed cloud account 130. The visualized infrastructure may be represented by a plurality of display elements 155, each corresponding to a virtual resource within the accessed cloud account 130. In response to selection of one of the display elements 155, the cloud resource monitoring system 100 provides access to additional portions of the collected data 140 in order to provide greater granularity as to the properties of the virtual resources associated with the selected display element.

Besides visualization of the cloud account 130, the cloud resource monitoring system 100 may be configured to perform analytics on the collected data 140 to determine a presence of any cybersecurity threats and/or misconfigurations. Based on this determination, the cloud resource monitoring system 100 generates alerts 160 to one or more administrators. The alerts 160 may include a portion of the analytic results and/or logic to mitigate or remediate any cybersecurity threats and/or misconfigurations. Content 165 from the alerts 160 may be rendered for display and further evaluation by an administrator.

As further shown in FIG. 1, the cloud resource monitoring system 100 may be configured to aggregate its analytic results with results from cloud resource monitoring system 102 to generate a single display (dashboard) to visually illustrate the presence of any potential cybersecurity threats or misconfigurations for cloud accounts 130, 132 from public cloud networks 110 ₁, 110 _(N). Additionally, or in the alternative, the cloud resource monitoring system 100 may be configured to retrieve and aggregate account data from cloud accounts 130, 132 residing in different public cloud networks 110 ₁, 110 _(N) (e.g., collected (account) data 140 along with account data received from the cloud account 132), perform analytics on the aggregated data, and generate a display (dashboard) on an electronic device (e.g., laptop 170 and/or smartphone 175) to visually illustrate the presence of any potential cybersecurity threats or misconfigurations for any of these cloud accounts 130 and/or 132. As a result, the cloud resource monitoring system 100 provides a scalable cloud security solution with rule-based analytics to provide visibility as to the security status of all cloud accounts (and services associated with these accounts) with retention and reporting of operational log data and audit compliance data.

Referring now to FIG. 2, a first exemplary embodiment of virtual resources within the first public cloud network 110 ₁ of FIG. 1 is shown, where the cloud resource monitoring system 100 operates as an independent, cloud-based hosted service that may handle cloud accounts for different customers. As shown, the cloud resource monitoring system 100 may be installed as a free or subscription-based services on the first public cloud network 110 ₁ by the cloud provider or a third-party source.

The cloud resource monitoring system 100 includes cloud visibility logic 200, namely logic that is configured to gain authorized access to the customer's cloud account 130, and once authorized access is secured, retrieve the collected data 140 (e.g., meta-information including operational log data) associated with the accessed cloud account 130 (operation A). Based on the collected data 140, the cloud visibility logic 200 is configured to (i) generate a representation 230 (operation B) that visualizes an infrastructure of the assessed cloud account 130 based on the collected data 140, (ii) perform analytics of the collected data 140 (operation C) to determine a presence of any cybersecurity threats or (setting) misconfigurations, and/or (iii) generate alerts 240 that are made available to one or more administrators of the analytic results (operation D). The alerts 240 may include messages with the analytic results and/or information for use in performing remediation activities including reverting a defined policy of operation for all or specific virtual resources utilized by the cloud account 130 under analysis, which is established through one or more settings or rules, to a default or predetermined configuration, if desired.

Herein, the cloud visibility logic 200 may be configured to secure authorized access to a particular customer's cloud account in a public cloud network using any of a number of authentication schemes. For example, one authentication scheme may feature a web user interface (Web UI) portal 300 of FIG. 3, which may be utilized at initial set-up in registration for monitoring services offered by the cloud resource monitoring system 100 or when the cloud visibility logic 200 determines that is not maintaining valid access tokens to gain authorized access to content within the cloud account 130 (e.g., authentication time period for the access token has expired, access token has been revoked, etc.).

As shown in FIG. 3, according to one embodiment of the disclosure, the Web UI portal 300 includes a plurality of entries 310. A first entry 312 may be reserved to receive an identifier for the cloud account 130 (e.g., account name, alias, etc.). Other entries 314 of the plurality of entries 310 may include access controls such as one or more keys (e.g., session keys, etc.), password(s), or the like. An optional entity 316 may include an identifier of a particular resource or resources in the public cloud network 110 ₁ to which the access token permits access. A customer credential is generated upon placing access control parameters into entries 310 and selecting the “Configure” area 318 and is provided to access control logic 250, which may reside as a virtual resource as part of the cloud account 130 as shown in FIG. 2 or as a separate service (not shown). The customer credential may be temporarily stored in the virtual data storage 220, perhaps until receipt of an access credential (token) 221 generated by and received from the access control logic 250.

Referring still to FIG. 2, once granted authorization to access the cloud account 130 (i.e., cloud resource monitoring system 100 currently maintains a valid access token 221 for the cloud account 130), according to one embodiment of the disclosure, the cloud visibility logic 200 may provide the access token 221 to the access control logic 250, which permits access to content within the cloud account 130. Thereafter, the cloud visibility logic 200 may accumulate the collected data 140, namely account data such as operational log data and/or other meta-information for example. The operational log data and/or other meta-information, forming the collected data 140, may be accumulated during the processing of software components by virtual compute resources 260 (e.g., one or more virtual compute engines each based on operability of a hardware processor and allocated to the cloud account 130) and maintained within virtual storage resources 270 (e.g., one or more virtual data stores each operating as non-tangible storage medium allocated to the cloud account 130). Additionally, the software components may be stored within the virtual storage resources 270 allocated to the cloud account 130. As an alternative, the cloud visibility logic 200 may collect the account data 140, but this collected data 140 may be stored within one or more virtual data stores (not shown) outside of the memory allocated to the cloud account 130.

As described above, the cloud visibility logic 200 may perform analytics on the collected data 140 (e.g., operational log data, meta-information associated with certain virtual resources, etc.) to detect a cybersecurity threat and/or cloud account misconfiguration. According to one embodiment of the disclosure, the analytics may involve one or more analyses of operational log data (e.g., content 280 from API logs, flow data 285 identifying which users are connecting to virtual private clouds being part of the cloud account 130, meta-information 290 directed to settings of the virtual compute engines within the virtual compute resources 260, etc.), which are conducted by one or more virtual compute engines 260 operating in accordance with a plurality of rules, such as correlation rules 295 that are configured to identify an occurrence of suspicious events (e.g., one or more unexpected, abnormal or inconsistent events) or regulatory compliance rules to verify compliance with governmental or other regulations regarding data acquisition and/or retention. The analyses may involve a matching of events associated with the collected data 140 with patterns of known suspicious events, which may involve an initial temporal analysis being conducted to order these events based on time of occurrence.

Additionally, or in the alternative, the analyses may involve a comparison of the current snapshot of the state of the cloud account 130 against prior snapshots. Thereafter, an analysis is conducted on the differences between these snapshots to determine changes in the cloud account 130. For both of these analyses, the cloud visibility logic 200 operates to determine potential issues, such as cybersecurity threats or misconfigurations that may be causing the virtual resources for the cloud account 130 to operate incorrectly, inconsistently, or in a less than optimal manner. As yet another analysis (or alternative analysis), although not shown, a determination of a cybersecurity threat may be further established by correlating additional meta-information collected by the cloud visibility logic 200 with other intelligence such as data pertaining to suspicious events associated with cybersecurity threats (malicious events) and/or account misconfigurations received from other sources (e.g., third party intelligence, post-intrusion intelligence, pre-attack intelligence). The correlation of the analytic results from one or more of these analyses may correspond to a threat/misconfiguration score that denotes a threat or misconfiguration upon exceeding a prescribed threshold.

If cybersecurity threat or account misconfiguration is detected by the cloud visibility logic 200, the alert 240 may be generated and issued to one or more administrators. The alert 240 may include information that, once received and rendered in a displayable format, represents the events (e.g., activities) that led to the cybersecurity threat or account misconfiguration. The alert 240 may allow for the customer's administrator to conduct a retrospective review of activities associated with a particular virtual resource or a particular group of virtual resources over a prescribed duration, based on historical operational data associated with compromised or misconfigured cloud-based virtual resource.

Additionally, the alert 240 may include a prescribed mitigation scheme to remediate the cybersecurity threat or account misconfiguration, which may be triggered automatically or by the administrator (e.g., selecting a radio button or link to provide further information of the threat/misconfiguration and potential mitigation processes available). The alert 240 and/or prescribed mitigation scheme may be configured in accordance with a set of regulatory compliance rules associated with, for example, regulatory compliance (e.g., Health Insurance Portability and Accountability Act (HIPAA), Payment Card Industry Data Security Standard (PCI DSS), etc.).

Referring to FIG. 4A, a second exemplary embodiment of virtual resources within the first public cloud network 110 ₁ of FIG. 1 is shown, where the cloud resource monitoring system 100 is installed within a customer's cloud account 130. The cloud resource monitoring system 100 includes the cloud visibility logic 200, which is configured to gain authorized access to resources within the customer's cloud account 130. For example, the cloud visibility logic 200 may retrieve the collected data 140, namely operational log data and/or other meta-information for example, which may be generated during the processing of software components by virtual compute engines (VCEs) 400 of the virtual compute resources 260 and/or stored within one or more virtual data stores 410 of the virtual storage resources 270. The collected data 140 may be subsequently stored within the virtual data storage 220 allocated for use by the cloud resource monitoring system 100.

Once authorized access is secured (e.g., in possession of valid access tokens 221 to specific virtual resources), the cloud visibility logic 200 is configured to retrieve account data, including meta-information such as operational log data associated with or maintained by those specific virtual resources. As shown, in lieu of providing access tokens 221 outside of the cloud account 130, for this embodiment, the access tokens 221 are maintained within the cloud account 130 based on communications initiated by the UI web portal 300 of FIG. 3 (operation A).

Operating in a manner similar to a deployment external to the cloud account 130 as illustrated in FIG. 2, the cloud visibility logic 200 may be configured to (i) generate a representation 420 (operation B) to visualize an infrastructure of the cloud account 130 based on the collected data 140, (ii) perform analytics of the collected data 140 (operation C) to determine a presence of any threats or misconfigurations, and (iii) perform activities to generate alerts 430 that are made available to one or more administrators of the analytic results (operation D). The alerts 430 may include messages with the analytic results and/information for use in performing remediation activities, as described above.

Although not shown, the cloud visibility logic 200 may establish communications with other cloud accounts within the public cloud network 110 ₁ in which cloud account 130 resides, or with other cloud accounts in a different public cloud network, such as cloud account 132 residing in public cloud network 110 _(N) of FIG. 1. The cloud visibility logic 200 may be configured to generate another visualization of the infrastructure of the cloud account 132 based on the collected operational log data or other meta-information, perform analytics of the collected operational log data or other meta-information to determine a presence of any cybersecurity threats or account misconfigurations, and include the analytics and/or visualization within the downloaded data provided via the alerts 430.

Referring now to FIG. 4B, an exemplary embodiment of virtual resources within the cloud visibility logic 200, as illustrated of FIG. 4A as well as FIG. 2 (above) is shown. Herein, virtual compute resources 260 are configured to process software components maintained within the virtual storage resources 270, including the cloud visibility logic 200. In particular, the virtual compute resources 260 may include one or more virtual compute engines 400, namely processor instances that are configured to execute software components of the cloud visibility logic 200 stored within the virtual storage resources 270. Examples of software components forming the cloud visibility logic 200 may include, but are not limited or restricted to credential evaluation logic 450, data collection logic 455, visualization logic 460, correlation logic 465, reporting logic 470, remediation logic 475, update logic 480 and aggregation logic 485.

Herein, when executed by one or more virtual compute engine 400 included as part of the virtual compute resources 260, the credential evaluation logic 450 is configured to determine whether the cloud visibility logic 200 is permitted access content from the cloud account 130. This determination may be based on an internal check as to whether the stored access token 221 is valid and may be used by the cloud visibility logic 200 to gain access to content within the cloud account 130. If the access token 221 is not valid (e.g., expired, revoked, etc.), the credential evaluation logic 450 is further configured to select a particular authentication operation to be performed to obtain the valid access token. For instance, a detected lack of a valid access token may prompt the credential evaluation logic 450 to provide a web UI portal 300 of FIG. 3, which allows for entry of access control parameters (credentials) that may be either (i) authenticated to prompt return of a valid access token or (ii) used, either collectively or in part, to form the access token 221 to be uploaded into the virtual data storage 220 utilized by the cloud visibility logic 200.

As shown in FIGS. 4A-4B, where the cloud visibility logic 200 has access to valid access tokens for the cloud account 130, the data collection logic 455 may be configured to retrieve the account data 140 (e.g., operational log data) from the virtual storage resources 270. The account data 140 may include information that pertains to an event performed by a customer's cloud-hosted virtual resources (e.g., resources 260 and/or 270), where the “event” corresponds to an operation or a collection of operations conducted by the virtual compute engines 400 that cause a change of state in the cloud infrastructure assigned to that customer.

As an illustrative example, an event may include an API call that is intended to create, modify, or read data, where information 280 associated with the API call may be stored within an entry of an API log being part of the account data 140, such as operational log data, within the assessed cloud account 130 of FIG. 1. The information gathered by the data collection logic 455 from an entry of the API log (i.e., API information 280) may correspond to one type of operational log data 140. Another type of operational log data 140 may be meta-information 290 associated with operations prompted by the API call (e.g., identifier of virtual compute engine(s) utilized, processing time, operating system version utilized, type of operation performed, results of such operations, etc.). The operational log data 140 may further include flow data 285 that includes meta-information associated with interconnectivity between virtual resources or other types of meta-information such as information directed to the customer's cloud account infrastructure.

Referring still to FIG. 4B, the correlation logic 465 is configured to conduct analytics associated with the events recovered as part of the collected data 140 to determine whether any of the events denote either (i) a potential cyberattack is or has been conducted or (ii) one or more account misconfigurations have occurred. The analyses by the correlation logic 465 may be conducted in accordance with a first subset of a plurality of rules 490, which are selected to identify an occurrence of one or more unexpected, abnormal or inconsistent events. The rules 490 may include subsets of rules, where each rule subset controls operations of a specific logic type operating within the cloud visibility logic 200, the data collection logic 455, the visualization logic 460, the correlation logic 465, the reporting (alert generation) logic 470, the remediation logic 475, the update logic 480 and the aggregation logic 485. This control of operation is referred to as a “defined policy” of operation.

The update logic 480 is configured to modify (e.g., add, change, or delete) any of the rules 490, any of the parameters associated with or utilized by the rules 490, and/or functional characteristics of one or more software components forming the cloud visibility logic 200. For example, the update logic 480 may be configured to perform modifications to the software components in a periodic or aperiodic manner based on modified information (e.g., software updates or patches, rule parameter changes, setting changes, etc.) from an external source. The source may include an entity in charge of maintaining the public cloud network 110 ₁, a provider of the cloud visibility logic 200, a provider of a software component installed within the cloud visibility logic 200, or the like.

The analyses by the correlation logic 465 may involve a matching of events associated with the collected data 140 with patterns of known malicious or compromising events, which may involve an initial temporal analysis being conducted to order these events based on time of occurrence. Additionally, or in the alternative, the analyses by the correlation logic 465 may involve a comparison of the current snapshot of the state of the cloud account 130 against prior snapshots.

Optionally, when implemented, the virtualization logic 460 is configured to receive a portion of the collected data 140 and generate a visualization of the infrastructure of the cloud-hosted virtual resources allocated for the cloud account 130. The visualized infrastructure may be used to identify certain portions of these cloud-hosted virtual resources that may be compromised or misconfigured based on analyses of the collected data 140 by the correlation logic 465. More specifically, the virtualization logic 460 may highlight or visually enhance display elements associated with the compromised or misconfigured virtual resources to better identify virtual resources that may require a more detailed review as a part of a cybersecurity attack or a part of an account misconfiguration.

After the correlation logic 465 completes the above-described analytics, the reporting logic 470 may control the issuance of the alerts 440 to one or more administrators responsible for managing the customer cloud-hosted resources or one or more administrators of the public cloud network, especially upon detection of a cybersecurity threat. Prior to issuance of the alerts 440, the aggregation logic 485 may be configured to aggregate analytic results produced by the correlation logic 465 with results from another cloud visibility logic. Additionally, or in the alternative, the cloud resource monitoring system 100 may be configured to retrieve and aggregate data (e.g., operational log data) received from cloud accounts residing in different public cloud networks, perform analytics on the aggregated data, and generate a display (dashboard) to visually depict the presence of any potential cybersecurity threats or misconfigurations for any of these cloud accounts

Additionally, for compliance with certain cloud policies, upon detection of a potential threat and/or misconfiguration, the remediation logic 475 may initiate actions to remediate the detected threat and/or misconfiguration through blocking, reconfiguring settings, or the like.

Referring now to FIG. 5A, an exemplary embodiment of a dashboard 500 generated by the reporting logic 470 of FIG. 4B is shown. The dashboard 500 is configured to support communications with an administrator utilizing cloud account management services provided by cloud resource monitoring system 100. The dashboard 500 includes a navigation window 510, a secondary window 520 and a search window 530. The navigation window 510 includes display elements 515 that, when selected, cause content to be loaded into the secondary window 520.

For example, as shown in FIG. 5B, an exemplary embodiment of a first navigational tool 535 of the dashboard 500 of FIG. 5A is shown. The first navigational tool 535 is activated in response to selection of the “inventory” display element 525 within the navigation window 510. Upon selection of the “inventory” display element 525, the cloud visibility logic 200 of FIG. 5A aggregates groups of different virtual resources (e.g., virtual compute engines 540, virtual data stores 541, virtual private clouds 542, etc.) and generates resource display elements 540-542 to represent these virtual resources. For instance, as shown, a first resource display element 540 may be directed to identifying a number of virtual compute engines being allocated to the cloud account 130 of FIGS. 1, 2 and 4A. Upon further selection of the first resource display element 540, a listing of each of the virtual compute engines and its properties (e.g., name, processing capability, etc.) may be generated for display.

Additionally, a second display element 541 may be directed to identifying a number of virtual data stores being allocated for and utilized by the cloud account 130. Upon further selection of the second display element 541, a listing of each of the virtual data store and its characteristics (e.g., name, storage capacity, unused storage capacity, etc.) may be generated for display as an overlaying window for example. Also, a third display element 542 may be directed to identifying a number of virtual private clouds (VPCs) utilized by the cloud account 130. Upon selection of the third display element 542, a listing of each the virtual private clouds and its properties (e.g., name, IP address, etc.) may be generated for display.

Referring now to FIG. 5C, an exemplary embodiment of a second navigational tool 550 of the dashboard 500 of FIG. 5A is shown. Upon selection of an “infrastructure” display element 526, the cloud visibility logic 200 is configured to generate a display 560. The display 560 features a plurality of display elements 562 ₁-562 _(R) (R>1), where the display elements 562 ₁-562 _(R) correspond to virtual resources formulating an infrastructure of the cloud account 130. Some or all of these display elements 562 ₁-562 _(R) may be implemented as nested display elements that are visible upon selection of the “details” icons 564 ₁-564 _(R). For instance, a first display element 562 ₁ may represent a virtual private cloud (VPC) identifying the name of the VPC and its Internet Protocol (IP) address. However, upon selection of the details icon 564 _(R) of the display element 562 _(R), one or more display sub-elements 570 ₁-570 _(S) (S≥1) are rendered, each representing a particular zone within the VPC or one or more particular virtual resources (e.g., virtual compute engines, virtual data stores, etc.) within that VPC. As described below, each display sub-elements 570 ₁-570 _(S) provides a selectable icon to obtain further information associated with each of the virtual resources.

Referring now to FIG. 5D, an exemplary embodiment of a third navigational tool 580 of the dashboard 500 of FIG. 5A is shown. Upon selecting an “activity” display element 527, the reporting logic 470 is configured to generate a display including a timeline 585 of events 590 conducted by virtual resources within the customer's cloud account 130 that are determined to be a “malicious” event; namely an event associated with a cyberattack or an account misconfiguration. The timeline 585 provides a chronological sequence of the malicious or compromising events and allows for retrospective review of events based on any of a plurality of criterion such as a date/time range, event (activity) type, particular virtual resource represented by resource identifier, source, or the like.

As shown, each of these malicious or compromising events 590 identified on the timeline may include an identifier of a virtual resource 591, date/time of detection 592, a name 593 of a detected activity associated with the virtual resource, an identifier 594 of an original source of content that causes the occurrence of the “malicious” event, or the like. Herein, the event timeline 590 may provide guidance for conducting an in-depth analysis of the cause of the malicious or compromising event by selection of the “more” data display element 595 that, when selected, provides for display additional details surrounding the activity (e.g., activity type, additional source details, etc.) as shown herein.

Referring to FIG. 6, an exemplary embodiment of a hosted service (on-premises) deployment for the cloud visibility logic 200, which is installed within an on-premises electronic device 600 configured to access and retrieve meta-information, including operational log data, from user account information for on-premises analysis is shown. The electronic device 600 includes a hardware processor 602, storage medium (e.g., memory) 604 and a network interface 606, which are communicatively coupled together via one or more transmission mediums 608, for establishing and maintaining communications with the public cloud network 110 ₁. The cloud visibility logic 200 is deployed within the memory 604 and executed by the processor 602.

Herein, as described above, the cloud visibility logic 200 may be configured to gain authorized access to the customer's cloud account 130 in the first public cloud network 110 ₁ using a selected authentication scheme. Similar to the cloud-based hosted service operations illustrated in FIG. 2, the cloud visibility logic 200 may transmit a permission request message 610 from the electronic device 600 to an endpoint device 620 if the cloud visibility logic 200 determines that its stored access tokens for use in gaining authorized access to stored content within the cloud account 130 residing in the first public cloud network 110 ₁ or the cloud account 132 residing in the N^(th) public cloud network 110 _(N) are invalid. The endpoint device 620 is an electronic device utilized by the customer to which the cloud accounts 130 and 132 pertain.

As a first illustrative authentication scheme, upon receipt of the permission request message 610, the Web UI portal 300 is launched for display by the endpoint device 620. As set forth in FIG. 3, as described above, the first entry 312 may be reserved to receive an identifier for the cloud account 130 (e.g., account name, alias, etc.). Other entries 314 and 316 may include key(s) or another type of credential and/or virtual resource identifier, respectively. The contents of the Web UI portal 300 are collected and, based on these contents, a first customer credential 630 is provided to the cloud visibility logic 200 within the electronic device 600. The cloud visibility logic 200 may forward the first customer credential 630 to access control logic 640 within the public cloud network 110 ₁, which analyzes the first customer credential 630, and upon authentication, returns an access token 632 upon determination that the customer is permitted access to the cloud account 130 via the cloud visibility logic 200.

Alternatively, as a second illustrative example, the authentication scheme to securing an access token 652 may be conducted by the cloud visibility logic 200 through an OAuth 2.0 Authorization Framework or a similar framework. For example, the cloud visibility logic 200 may be registered by an authorized administrator as logic permitted to operate as an agent for a customer in gaining access to stored data within the cloud account 132. During registration, in response to the permission request message 610, an administrator for the cloud visibility logic 200 may provide a second customer credential 650 (e.g., one or more network addresses), which may be different from the first customer credential 630 given communications are directed to a different type of public cloud network, for accessing stored content within the cloud account 132. Upon registration, based on the second customer credential 650, an access control logic 654 (residing in the public cloud network 110 _(N)) may return a result of an authentication of the customer credential (Success/Failure) and the access token 652 assigned to the customer for use in accessing the cloud account 130 for a prescribed period of time or until the token 652 is revoked.

Once a valid access token is available to the cloud visibility logic 200 (e.g., access token 632), the cloud visibility logic 200 may issue a communication session to access stored content within the cloud account 130. The communication session may include a scan request message 660, which includes the access token 632 and seeks authorization to access the stored content with the cloud account 130 in order to perform analytics to identify whether the cloud account 130 has been potentially compromised. The cloud visibility logic 200 may receive a returned response 662 to the scan request message 660, which may include meta-information 664, such as operational log data associated with the accessed cloud account 130. The meta-information 664 may be directed to software components forming an infrastructure of the access cloud account 130, such as information directed to the virtual compute engines 400 and/or virtual data stores 410 allocated to the customer's cloud account 130. Additionally, or in the alternative, the meta-information 664 may be associated with events acquired and/or generated through processing operations conducted by the virtual compute engines 400 allocated to the customer's cloud account 130.

In general, the meta-information 664 may be content associated with an operation or a collection of operations conducted by the virtual resources that represent an attempted change of state in the cloud account 130 or properties associated with virtual resource, or more restrictive as content directed to events that pertain to an operation or a collection of operations conducted by the virtual resources that is unexpected, abnormal or inconsistent with typical operations within the cloud account 130. Specifically, the events may include queries to permission restricted data stores to obtain sensitive information disability or enabling certain operability (e.g., encryption, change ciphers, etc.). Additionally, the events may include attempted accesses to cloud accounts in the same or other public cloud networks such as attempts to access the cloud account 132 residing in the public cloud network 110 _(N).

The cloud visibility logic 200 may perform analytics on the collected meta-information 664 to detect a cybersecurity threat and/or cloud account misconfiguration. According to one embodiment of the disclosure, the analytics may involve one or more analyses on a portion or portions of the meta-information 664 in accordance with a plurality of rules 670 that are configured to identify an occurrence of unexpected, abnormal or inconsistent events. As described above and illustrated in FIG. 5B, the rules 670 may be modified by update logic within the cloud visibility logic 200. Also, the analyses may involve a matching of events included as part of the meta-information 664 with patterns of known malicious or compromising events, or a comparison of the current snapshot of the state of the cloud account 130 against the prior snapshots in order to identify differences and concentrate subsequent analyses of these differences. For either or both of these analyses, the cloud visibility logic 200 operates to determine potential issues, such as cybersecurity threats or misconfigurations that may be causing the virtual resources for an account to operate incorrectly, inconsistently, or in a less than optimal manner.

If cybersecurity threat or account misconfiguration is detected by the cloud visibility logic 200, an alert 680 may be generated by the cloud visibility logic 200 within the on-premises electronic device 600 for issuance to one or more administrators. The alert 680 may include information associated with the analytics, where these analytic results may be rendered in a display format to represent the particular events that led to the cybersecurity threat or account misconfiguration. Additionally, the alert 680 may include a prescribed mitigation scheme to remediate the cybersecurity threat or account misconfiguration, which is in compliance with any regulatory requirements.

Although not shown in detail, the cloud visibility logic 200, with access to the valid access token 652, may issue a communication session to access stored content within the cloud account 132 in order to gain access to stored content (e.g., operational log data, meta-information, etc.) with the cloud account 132 in order to perform analytics to identify whether the cloud account 132 has been potentially compromised as well. The cloud visibility logic 200 provides a centralized analytic and alert scheme to allow administrator or analyst to review the security status of cloud resources for a customer, whether these cloud resources pertain to a single cloud account, multiple cloud accounts within the same public cloud network or multiple cloud accounts within different public cloud networks, a combination of cloud resources within cloud account(s) and resources within an enterprise network to which the electronic device 600 is connected. This review may be provided via the same dashboards as shown in FIGS. 5A-5D thereby providing a “single pane” security visibility across enterprise and cloud infrastructures.

Referring now to FIG. 7, an exemplary embodiment of a hybrid cloud management system 700 including cloud visibility data collection logic 710 maintained at the first public cloud network 110 ₁ and cloud visibility analytic logic 720 maintained at an on-premises electronic device 600. As shown, cloud visibility data collection logic 710 may be configured to (i) gain authorized access to resources within the customer's cloud account 130 (operations A & B), and once authorized access is secured, (ii) collect data 730 (operation C), including meta-information such as operational log data associated with the cloud account 130. As shown, the cloud visibility data collection logic 710 is installed as a resource within the cloud account 130 so that access tokens are secured and maintained therein. Of course, the cloud visibility data collection logic 710 may be installed within the cloud resource monitoring service 210, and if so, the cloud visibility data collection logic 710 would secure the access tokens for the cloud account 130 and receive the collected data 730 therefrom.

The cloud visibility analytic logic 720 processes and analyses the collected data 730 returned from the cloud visibility data collection logic 710 (operation D). The processes and analyses conducted by the cloud visibility analytic logic 720 involve the generation a graphical representation 740 to visualize an infrastructure of the cloud account 130 based on the collected data 730 (operations E&F) and the performance of analytics on the collected data 730 to determine a presence of any threats or misconfigurations. Based on these analytics, the cloud visibility analytic logic 720 may generate alerts 750 that are made available to one or more administrators of the analytic results (operation G). The alerts 750 may include messages with the analytic results and/information for use in performing remediation activities, as described above.

V. Operational Flow—Cloud Management System

Referring now to FIG. 8, an exemplary flowchart of the operations conducted by the cloud resource monitoring system 100 is shown. Initially, authorized access to a cloud account for a targeted customer is requested and secured (block 800). From the accessed cloud account, operational log data is retrieved (block 810). The operational log data may include meta-information associated with events each corresponding to an operation or a collection of operations conducted by the virtual resources within the cloud account that cause a change of state in the infrastructure of the cloud account. For example, the operational log data may include content stored within an entry of an API call that is directed to an API call intended to create, modify, or read data. The data within an entry of the API log is one type of operational log data. Other examples of an event may include recorded characteristics and/or operability of a virtual resource such as a virtual compute engine or virtual data store, or the like. Examples of recorded operability may include a critical action such as disabling a security service, disabling encryption on stored data resources.

As an optional operation, based on the operational log data, a visual display of an infrastructure of the cloud account may be generated (block 820). According to one embodiment, the visual display may include a plurality of display elements corresponding to the virtual resources formulating the cloud account, where the positioning of these display elements (or generation of connectors between these display elements) identify relationships between the virtual resources. For changes in infrastructure that are unexpected, abnormal or inconsistent events, the display elements (or connectors) may be highlighted to identify an attempted cyberattack or account misconfiguration.

Thereafter, analytics are conducted on the recovered operational log data to determine whether a cyberattack has or is being attempted or a misconfiguration of the cloud account has occurred (blocks 830-850). When the analytic results identify that a cyberattack has or is being attempted on resources allocated to the cloud account and/or the cloud account has been misconfigured (e.g., unexpected setting change in the cloud account, abnormal setting, events occurring that are inconsistent with known (expected) patterns of events, etc.), one or more alerts may be generated and provided to administrators for the customer that is associated with the cloud account (block 860). The alerts may include a portion of the analytic results that are used in identifying the attempted cyberattack and/or account misconfiguration along with context information associated with the attempted cyberattack and/or account misconfiguration. Included as part of the alert, information directed to the remediation of the attempted cyberattack and/or account misconfiguration in compliance with any regulatory rules is provided (block 870).

In the foregoing description, the invention is described with reference to specific exemplary embodiments thereof. However, it will be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. 

What is claimed is:
 1. A system for protecting public cloud-hosted virtual resources, comprising: a processor; and a memory communicatively coupled to the processor and configured to store cloud visibility logic, the cloud visibility logic including credential evaluation logic that, when executed by the processor, is configured to gain authorized access to a cloud account within a first public cloud network, data collection logic that, when executed by the processor, is configured to retrieve account data from the cloud account, correlation logic that, when executed by the processor, is configured to conduct analytics on the account data to determine whether the cloud account is subject to a cybersecurity threat or misconfiguration, aggregation logic configured to receive and aggregate analytic results generated by the correlation logic and analytic results generated by a second cloud visibility logic configured to perform analytics on account data associated with a second cloud account maintained within a second public cloud network different than the public cloud network, and reporting logic that, when executed by the processor, is configured to generate an alert when the cloud account or the second cloud account is determined to be subject to the cybersecurity threat or misconfiguration.
 2. The system of claim 1, wherein the credential evaluation logic is configured to gain authorized access to the cloud account by submission of a valid access token to logic that controls access to at least the cloud account.
 3. The system of claim 1, wherein the credential evaluation logic to obtain the valid access token by generating for display a web user interface portal to receive as input information that, upon authenticated, prompts return of a valid access token.
 4. The system of claim 1, wherein the processor corresponds to a virtual compute engine instance associated with a hardware processor and the memory corresponds to one or more virtual data stores associated with a non-transitory storage medium.
 5. The system of claim 1, wherein the account data includes operational log data pertaining to one or more events performed by the public cloud-hosted virtual resources that cause a change of state in an infrastructure of the targeted cloud account.
 6. The system of claim 5, wherein the operational log data include meta-information associated with one or more Application Programming Interface (API) calls stored within an API log.
 7. The system of claim 1, wherein the cloud visibility logic further comprises a visualization logic that, when executed by the processor, is configured to receive a portion of the account data including data associated with an infrastructure of the cloud account and generate a visualization of the public cloud-hosted virtual resources forming the infrastructure of the cloud account.
 8. The system of claim 7, wherein the visualization logic to highlight or visually enhance one or more display elements of the virtualization of the infrastructure of the cloud account that correspond to potentially compromised or misconfigured public cloud-hosted virtual resources.
 9. The system of claim 1, wherein the cloud visibility logic further comprises remediation logic to initiate one or more actions to remediate the cybersecurity threat to or misconfiguration of the cloud account, the one or more actions include reverting a policy of operation for one or more of the public cloud-hosted virtual resources utilized by the cloud account to a default or predetermined configuration, the policy of operation being established through one or more settings or rules.
 10. A system for protecting public cloud-hosted virtual resources, comprising: a processor, and a memory communicatively coupled to the processor and configured to store cloud visibility logic, the cloud visibility logic comprises credential evaluation logic that, when executed by the processor, is configured to gain authorized access to a cloud account within a first public cloud network, data collection logic that, when executed by the processor, is configured to retrieve account data from the cloud account, correlation logic that, when executed by the processor, is configured to conduct analytics on the account data to determine whether the cloud account is subject to a cybersecurity threat or misconfiguration, aggregation logic configured to receive and aggregate account data, including operational log data, associated with a second cloud account maintained within a second public cloud network different than the public cloud network, the correlation logic to perform analytics on the account data from the cloud account and the account data from the second cloud account maintained within the second public cloud network, and reporting logic that, when executed by the processor, is configured to generate an alert when the cloud account or the second cloud account is determined to be subject to the cybersecurity threat or misconfiguration.
 11. The system of claim 10, wherein the cloud visibility logic further comprises update logic configured to update the rules that control operability of any one or more of the following: the credential evaluation logic, the data collection logic, the correlation logic, the reporting logic, and the aggregation logic.
 12. A computerized method for protecting public cloud-hosted virtual resources, comprising: gaining authorized access to a cloud account within a first public cloud network; retrieving account data from the cloud account; conducting analytics on the account data to determine whether the cloud account is subject to a cybersecurity threat or misconfiguration; aggregating analytic results associated with the account data from the cloud account by the correlation logic and analytic results based on analytics conducted on account data associated with a second cloud account maintained within a second public cloud network different than the first public cloud network; and generating an alert when the cloud account is determined to be subject to the cybersecurity threat or misconfiguration.
 13. The computerized method of claim 12, wherein authorized access to the cloud account is gained by submitting a valid access token to logic that controls access to at least the cloud account.
 14. The computerized method of claim 13, wherein prior to submitting the valid access token, obtaining the valid access token by generating for display a web user interface portal to receive as input information that, upon authenticated, prompts return of a valid access token.
 15. The computerized method of claim 12, wherein the account data includes operational log data pertaining to one or more events performed by the public cloud-hosted virtual resources that cause a change of state in an infrastructure of the cloud account.
 16. The computerized method of claim 15, wherein the operational log data include meta-information associated with one or more Application Programming Interface (API) calls stored within an API log.
 17. The computerized method of claim 12 further comprising: receiving a portion of the account data including data associated with an infrastructure of the cloud account and generating a visualization of the public cloud-hosted virtual resources forming the infrastructure of the cloud account.
 18. The computerized method of claim 17 further comprising: highlighting or visually enhancing one or more display elements of the virtualization of the infrastructure of the cloud account that corresponds to potentially compromised or misconfigured public cloud-hosted virtual resources.
 19. The computerized method of claim 12 further comprising: initiating one or more actions to remediate the cybersecurity threat to or misconfiguration of the cloud account, the one or more actions include reverting a policy of operation for one or more of the public cloud-hosted virtual resources utilized by the cloud account to a default or predetermined configuration, the policy of operation being established through one or more settings or rules. 